Physiological measurement logic engine

ABSTRACT

A patient monitor including a physiological measurement logic engine receives physiological data from a physiological sensor. The logic engine abstracts one or more features of the physiological data and determines a category for the abstracted feature. The logic engine further encodes the category of each of the one or more features and determines an action to perform based on the encoded categories.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 15/634,745, filed Jun. 27, 2017, entitled “Physiological Measurement Logic Engine,” which is a continuation of U.S. patent application Ser. No. 14/967,075, filed Dec. 11, 2015, entitled “Physiological Measurement Logic Engine,” which is a continuation of U.S. patent application Ser. No. 13/425,085, filed Mar. 20, 2012, entitled “Physiological Measurement Logic Engine,” which is a continuation of U.S. patent application Ser. No. 13/272,038, filed Oct. 12, 2011, entitled “Physiological Measurement Logic Engine,” which claims priority benefit of U.S. Provisional Patent Application No. 61/392,863, filed Oct. 13, 2010, entitled “Physiological Measurement Logic Engine,” each of which is hereby incorporated by reference herein in its entirety.

FIELD

The present disclosure relates to non-invasive biological parameter sensing, including sensing using optical and/or acoustic sensors and related systems and methods.

BACKGROUND

Patient monitoring of various physiological parameters of a patient is important to a wide range of medical applications. Pulse oximetry is one of the techniques that have developed to accomplish the monitoring of some of these physiological characteristics. Pulse oximetry relies on a sensor attached externally to a patient to output signals indicative of various physiological parameters, such as a patient's constituents and/or analytes, including for example a percent value for arterial oxygen saturation, carbon monoxide saturation, methemoglobin saturation, fractional saturations, total hematocrit, billirubins, perfusion quality, or the like. A pulse oximetry system generally includes a patient monitor, a communications medium such as a cable, and/or a physiological sensor having light emitters and a detector, such as one or more LEDs and a photodetector. The sensor is attached to a tissue site, such as a finger, toe, ear lobe, nose, hand, foot, or other site having pulsatile blood flow which can be penetrated by light from the emitters. The detector is responsive to the emitted light after attenuation by pulsatile blood flowing in the tissue site. The detector outputs a detector signal to the monitor over the communication medium, which processes the signal to provide a numerical readout of physiological parameters such as oxygen saturation (SpO2) and/or pulse rate.

High fidelity patient monitors capable of reading through motion induced noise are disclosed in U.S. Pat. Nos. 7,096,054, 6,813,511, 6,792,300, 6,770,028, 6,658,276, 6,157,850, 6,002,952 5,769,785, and 5,758,644, which are assigned to Masimo Corporation of Irvine, Calif. (“Masimo Corp.”) and are incorporated by reference herein. Advanced physiological monitoring systems can incorporate pulse oximetry in addition to advanced features for the calculation and display of other blood parameters, such as carboxyhemoglobin (HbCO), methemoglobin (HbMet), total hemoglobin (Hbt), total Hematocrit (Hct), oxygen concentrations, glucose concentrations, blood pressure, electrocardiogram data, temperature, and/or respiratory rate as a few examples. Typically, the physiological monitoring system provides a numerical readout of and/or waveform of the measured parameter. Advanced physiological monitors and multiple wavelength optical sensors capable of measuring parameters in addition to SpO2, such as HbCO, HbMet and/or Hbt are described in at least U.S. patent Ser. No. 11/367,013, filed Mar. 1, 2006, titled Multiple Wavelength Sensor Emitters, now issued as U.S. Pat. No. 7,764,982, and U.S. patent application Ser. No. 11/366,208, filed Mar. 1, 2006, titled Noninvasive Multi-Parameter Patient Monitor, assigned to Masimo Laboratories, Inc. and incorporated by reference herein. Further, noninvasive blood parameter monitors and optical sensors including Rainbow™ adhesive and reusable sensors and RAD-57™ and Radical-7™ monitors capable of measuring SpO2, pulse rate, perfusion index (PI), signal quality (SiQ), pulse variability index (PVI), HbCO and/or HbMet, among other parameters, are also commercially available from Masimo Corp. of Irvine, Calif.

Another physiological monitoring system uses sensors that include piezoelectric membranes located on or near a patient's body to measure body sounds. The body sounds can then be analyzed to determine ventilation, apnea, respiration rate, or other parameters. These monitors are referred to as acoustic respiratory monitors. Acoustic respiratory monitors are also commercially available from Masimo Corp. of Irvine, Calif.

SUMMARY

The present disclosure relates to a system for simplifying logic choices in a computing environment. In an embodiment physiological processing is simplified by abstracting relevant features, or general characteristics of the signal. As used herein, features and general characteristics are used interchangeably. In an embodiment, features of physiological signals are abstracted and are used in conjunction with a logic table in order to determine a course of action. In an embodiment, the abstracted features are used to provide a bit encoding scheme which directly relates to a specified result. In an embodiment, the system is used to encode logic choices relevant to display characteristics of the device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of an abstraction of the relative slopes of physiological signals.

FIG. 2 illustrates an example of an abstraction of the difference in outputs of different processing engines.

FIG. 3 illustrates an example of an abstraction of a trend line linear regression, and/or a standard deviation.

FIG. 4 is an expanded view of a lookup table that can be used by a patient monitor to determine what action to perform in view of the abstracted features.

FIG. 5 is a flow chart illustrating a process implemented by a patient monitor for determining what action to perform based on the abstracted features.

FIG. 6 is a flow chart illustrating an embodiment of a process implemented by a patient monitor for determining an appropriate action based on the features of a set of data.

FIG. 7 illustrates an embodiment of a patient monitoring system capable of abstracting features of physiological data.

FIG. 8 illustrates an example noninvasive multiparameter physiological monitor.

FIG. 9 illustrates an embodiment of an acoustic sensor system, which can provide physiological data to the patient monitoring system.

DETAILED DESCRIPTION Signal Analysis

Real time processing of physiological signals is often difficult and requires significant computing power, fast processors and significant power consumption and heat dissipation. Typical signal processing involves intensive and difficult mathematic operations in order to extrapolate useful data.

Feature Abstraction

One way to reduce the computational load in a physiological processing system is to abstract features of the signal. Feature abstractions use only relatively simple analysis which significantly reduces computational loads. Once abstracted, the features can then be used to make determinations about the physiological signals.

The difference between feature abstraction and typical computationally intensive signal processing is best understood with an analogy to human observations vs. computations. For example, consider the situation where Person A lives next to Person B. Person B brings their trash container out to the same position every time the trash is collected. Although Person A may not consciously note the position of the trash container, Person A is likely to notice that something is different if the trash container is placed in a different position. Importantly, that recognition can be made without measuring the exact position change of the trash container or even consciously noting the normal position of the trash container. Similarly, Person A may further note other changes regarding Person B. For example, Person A is likely to note that a different car is parked in Person B's driveway. Person A can make this determination without comparing old and new license plate numbers. Another example may be that Person A notes different children playing in Person B's yard. None of these abstractions or general observations required significant thought or specific measurements on the part of Person A. Similarly, features of physiological signals can be abstracted at various levels without significant computations.

Once abstracted, each feature can potentially indicate a number of possible explanations. For example, using the same analogy above, the change in location of Person B's trash container could indicate that a different family member took out the trash. However, coupling the change in location of trash container along with the different car and unfamiliar children playing in the yard may indicate that Person A has new neighbors. Importantly, the conclusion that Person A may have new neighbors is made without having direct knowledge of a change in neighbors or actually seeing the neighbors. Similarly, combinations of abstracted features provide different indications about the signal under analysis, while using relatively low processing power. However, it is to be understood that abstracting features of the signals described herein is significantly more complex and computationally intensive than the example given above. Furthermore, the abstraction of features of the signals (or data) described herein is typically done in real-time or near real-time using a digital signal processor, microcontroller, or other processor, operating at speeds far surpassing those of a human. For example, the processor may operate at hundreds, thousands, millions, billions, or even more cycles per second to ensure the features are abstracted in a timely manner. If the features are abstracted too slowly they lose their relevance.

In an embodiment, various features of a detected signal are abstracted. For example, in an embodiment, the relative slope of a signal over one or more windows of time is abstracted. In an embodiment, the relative noise level of a signal is determined. In an embodiment, the relative signal strength is determined. In an embodiment, comparisons between various features over different windows of time are compared and the comparison is an abstracted feature. In an embodiment, the features are abstracted in real-time or near real-time. Other abstractions can also be made as will be understood by those of skill in the art based on the present disclosure.

The examples provided below in FIGS. 1-3 are simplified examples of the types of abstractions that occur using the device described herein. It is to be understood that the calculations, computations, and abstractions are performed in real-time or near real-time at speeds surpassing those capable of a human. For example, the processor may perform hundreds, thousands, millions, billions or more calculations per second to determine the appropriate abstraction in real time or near real-time. In addition, the signals (or data) abstracted by the processor may be electrical signals, infrared signals, wireless signals, or other electro-magnetic wave signals that are incomprehensible to a human in their raw form and at the speeds communicated.

FIG. 1 illustrates an example of an abstraction of the relative slopes of physiological signals. As illustrated in FIG. 1, signals within two windows of time 102, 104 are analyzed. The windows can be any length of time. In an embodiment, each window is 30 seconds long. In another embodiment, each window is 60 seconds long. Other lengths of time can also be used. The windows can overlap or be non-overlapping in time. The signals in each window are then abstracted and characterized into one of five different slopes. These slopes are illustrated by the slope abstraction illustrator 114. For example, the relative slope of the signal within window 102 most closely matches slope 118. Similarly, the overall slope of the signal, or data, within window 104 most closely matches slope 130. By abstracting the overall slope of the signal into a relative slope, computations relevant to the signals are simplified. The overall slope of the signal may also be referred to as the trend of the signal. Although described with respect to five different slope abstraction values, more or fewer abstractions levels can be used. For example, one system might use 10 different abstraction slopes while another system might use three different abstraction slopes.

In an embodiment, after abstraction, the signal in each window is assigned a category. In the embodiment illustrated, the category is a bit code corresponding to the slope abstraction. In an embodiment, the slope of the signal in window 102, is matched to slope 118, and assigned bits “001.” Similarly, the slope of the signal in window 104 is assigned to bits “010.” As will be explained in greater detail below, bit assignments can be used to further simplify processing. Furthermore, as will be understood by those in the art from the present disclosure, the bit codes presented in the this example are not intended to be limiting and other bit codes, including different numbers of bits, can be used with the present disclosure.

In an embodiment, after abstracting the slopes of two or more signals in two or more windows of time, the slopes are then compared in order to determine a change in slope. The change in relative slope then provides another abstraction that can be used in further processing to make determinations regarding the signal. In an embodiment, this abstraction is also assigned a bit code based on the comparison. In an embodiment, the comparison is not necessary because the bit codes can be used in conjunction with the table described in FIG. 4 to designate an outcome based on the slopes without the necessity of further comparison computations. Thus, as described below, using the bit codes in association with FIG. 4 obviates the need the further processing and computational steps that might otherwise be necessary.

Another abstraction involves the comparison of two overlapping windows of data. This is illustrated, for example, in FIG. 2. Typically, physiological signals received from sensors are processed before being displayed. In processing the physiological signals, a patient monitor, described in more detail below with reference to FIGS. 7 and 9, performs any number of functions, computations, filters, and the like. The processing can account for signal noise, motion artifact, or any number of other signal distortions that can affect signal quality and the reliability of the output.

In an embodiment a patient monitor processes the data using one or more processing techniques, which may also be referred to as engines or processing engines, in parallel. The various engines can identify and filter specific signal distortions. For example, one engine can be configured to filter according to repetitive motion, while another engine can be configured to filter according to a single instance of motion. Other engines may be configured to filter or process the signals to account for other signal distortions, such as low signal-to-noise ratio, low signal power, low perfusion and the like. The use of parallel engines is described in U.S. Pat. No. 6,157,850, the disclosure of which is hereby incorporated by reference in its entirety.

With continued reference to FIG. 2, window 202 is an illustration of a physiological signal processed over a first time period, or window of time. Window 204 is an illustration of the same physiological signal processed over a different window of time, but that overlaps with the first window of time. This can be done using the same or different engines for each window of time. The x-axis 212 of the windows 202, 204 represents time, and the y-axis 214 of the windows 202, 204 represents signal amplitude. The data 220, 222 can be any type of physiological data, signal, or other data. Furthermore, the windows 202, 204 can be broken down into time the segments 210A, 210B, 210C, 210D, that divide the data based on a predefined time period. The predefined time period may be any size, ranging from less than a microsecond to minutes, hours or more. Typically, the data within the same time segments 210A, 210B, 210C, 210D of different windows 202 and 204 is similar. As noted in FIG. 2, the data 220, 222 is generally similar throughout most of the time segments 210A, 210B, 210C, 210D. However, in time segment 210A, data 206 and 208 are substantially dissimilar. The dissimilarities may be a result of differences in the processing. The dissimilarities may also be the result of different engines, where one engine is more suited for handling an event that occurred during time segment 210A, poor signal strength during time segment 210A, an error, or the like. Thus, one feature that the patient monitor can abstract is the difference in outputs between different engines and/or different windows of time.

In an embodiment, while abstracting the data, the patient monitor compares and identifies the difference between data 206 and data 208 in time segment 210A. The patient monitor categorizes the difference depending on various factors, such as type of data being analyzed, type of analysis being performed, engines being used, etc. In an embodiment, the difference is categorized as an insignificant difference, a minor difference, and/or significant difference. Based on the categorization, the patient monitor can implement a predefined action using a look-up table, which will be described in greater detail below, with reference to FIG. 4. Additional methods for categorizing the differences between the engine outputs may be used without departing from the spirit and scope of the description. Furthermore, the categories may be encoded using any number of different bit codes, as described above.

FIG. 3 is a plot diagram illustrating another embodiment of a feature abstraction, involving a trend line, linear regression, and/or standard deviation. Graph 300 illustrates an example of data measurements 306 over time. The x-axis 302 of graph 300 represents time and the y-axis 304 represents the amplitude of the measurements 306. The line 308 represents a trend line of the data measurements 306 over time. In an embodiment, the data measurements are normalized.

In an embodiment, the patient monitor computes a confidence value of the data measurements 306. The confidence value can be computed using the standard deviation, average, correlation coefficient and/or linear regression of the data measurements 306. For example, a high standard deviation and/or low correlation coefficient may be equated with a low confidence value, whereas a low standard deviation and/or high correlation coefficient may be equated with a high confidence value. Based on the confidence value, the data can be sorted into different categories indicating the level of confidence that can be placed in the data. For example, a relatively low confidence level may indicate that the signals are experiencing relatively large amounts of noise or other distortions, and that little confidence should be placed in the output. A relatively high confidence level may indicate that the patient monitor is experiencing relatively little noise in the system, and that high confidence can be placed in the output. The categories may be implemented using bit codes, described above with reference to FIG. 1. It is to be understood that more or fewer categories can be used to categorize the standard deviation of the data, or the trend line.

FIG. 4 is a block diagram illustrating an embodiment of an expanded view of an electronic lookup table (LUT) 400 implemented in the patient monitor. In an embodiment, the LUT 400 includes at least three sections: the features logic section 402, the expansion section 404, and the output section 406. The features logic section 402 is further broken down into three subsections 408, 410, 412. Each subsection 408, 410, 412 includes a bit encoding of the category of one abstracted feature. Each bit encoding is made up of multiple bits and/or bytes 414. The LUT 400 can be used by the patient monitor to determine what action to perform based on the category, or bit code, of the various features of the physiological data. It will be understood that the LUT 400 is only an example, and other embodiments with fewer or more sections, subsections, bit encodings, and features may be used without departing from the spirit and scope of the description.

As mentioned, LUT 400 includes three sections: the features logic section 402, the expansion section 404, and the output section 406. The patient monitor uses the feature logic section 402 and the expansion section 404 to “lookup” the action (encoded as the output 406) that is to be performed. Thus, each possible permutation of the featured logic section 402 and the expansion section 404 can have a corresponding output section 406. In other words, the output section 406 (or action) is selected as a function of the featured logic section 402 and the expansion section 404.

The feature logic section 402 is made up of one or more subsections 408, 410, and 412. Each subsection 408, 410, 412 can include one or more representations of categories of individual features in the form of individual bits and/or bytes 414. In the example illustrated, the features logic 402 includes three subsections 408, 410, 412. Each subsection 408, 410, 412 includes a bit code, made up of two bits, for a category of one individual feature. It will be understood that the feature logic section 402 can include fewer or more subsections and that the categories of the individual features may be represented with more or fewer bits as desired. For example, a greater number of categories may be desired for some features based on their complexity. As such, the features having more categories can use larger bit codes with more bits or bytes. Accordingly, in an embodiment, the bit codes for the different features are not uniform in their size. For example, one bit code for one feature may use two bits, while another bit code for another feature may use five bytes. In another embodiment, the bit codes are uniform in size for all features.

The expansion section 404 can include a number of subsections, similar to the subsections 408, 410, 412 of the feature logic section 402. The expansion subsections can include space, in the form of bits/bytes, for new features that are not included in the subsections 408, 410, 412. When not being used, the bits/bytes in the expansion section 404 can all be set to a logic ‘0’ or logic ‘1,’ as desired.

As mentioned earlier, the output section 406 is used by the patient monitor to determine the appropriate action in light of the feature logic section 402 and the expansion section 404. The patient monitor can use other logic as well in determining the appropriate output or action. The output section 406 can include a number of subsections similar to the feature logic section 402 and the expansion section 404. Furthermore, the actions to be taken by the patient monitor are encoded as bit codes within the output section 406. In an embodiment, each permutation of the feature logic section 402 and the expansion section 404 equates to a different bit code in the output section 406. In another embodiment, the bit code in the output section 406 for one or more permutations of the feature logic section 402 and the expansion section 404 is the same.

By abstracting the features and using the LUT 400, the patient monitor can reduce the amount of processing resources needed to perform the appropriate action given the set of data. Rather than processing the data itself, the patient monitor is able to abstract generalizations or general characteristics of the data and make determinations based on the general characteristics themselves. Thus, the patient monitor avoids processing the individual data itself. Even in those instances where analyzing or determining a feature is resource intensive, the patient monitor is able to reduce the overall amount of processing by reducing the number of items analyzed. For instance, instead of processing hundreds or even thousands of individual pieces of data, the patient monitor is able to process all, or a large number of, the pieces of data using a relatively small number of general characteristics that apply to the pieces of data in the aggregate. In addition, the use of a lookup table allows the actions or outputs to be predetermined, allowing the patient monitor to perform a simple “lookup” rather than repeatedly determining the appropriate action for each feature or piece of data analyzed. Furthermore, the lookup table can be implemented in hardware, further saving processing resources. Another benefit of the table is that in one embodiment there are no conditions left undefined. Often, in generating large and complex if/then statements in software, conditions are inevitably left out such that the device does not know what to do under an undefined condition. The table obviates this problem by inherently providing a result for every possible state.

FIG. 5 is a flow chart illustrating a process 500 implemented by a patient monitor for determining what action to perform based on the abstracted features. In an embodiment, the process 500 is executed in real-time or near real-time by the patient monitor. At block 504, the patient monitor obtains physiological data. The physiological data can be many various types of physiological data as described above. In some embodiments, the data need not be physiological data, as will be described in greater detail below.

At block 506, the patient monitor abstracts features of a set of data, or general characteristics. As described above, the features may include: differing engine outputs, standard deviation, slope, average, linear regression, correlation coefficient, and the like. Additional features may be used as well, such as time domain features, frequency domain features, and the like.

In abstracting the features, the patient monitor may analyze various general characteristics of the set of data in a variety of ways. For example, the patient monitor can abstract all the features or a subset of all the features. The subset can be determined based on the features that require, or are likely to use, relatively little processing resources, or can be determined randomly. In an embodiment, the patient monitor uses a list of predetermined features to determine which features to analyze. In an embodiment, the list of features is stored in the memory of the patient monitor. In another embodiment, the list is stored in memory remotely located from the patient monitor. In yet another embodiment, the patient monitor determines which features are to be abstracted based on the type of data being processed or based on the abstractions that are available to the monitor at any given point in time. For example, some features of data may be more pronounced or more easily determined based on the type of data received. For example, comparing the output of different engines of plethysmograph data may be less computationally intensive than calculating the standard deviation or linear regression of the plethysmograph data. In such an instance, the patient monitor can select to abstract the comparison between the data engines and not calculate the standard deviation or linear regression. In another embodiment, the patient monitor determines both abstractions. In an embodiment, the determination of which abstraction to use is based on a confidence level for each abstraction. In an embodiment, each abstraction is further given a confidence bit code to indicate a confidence level of that abstraction.

At block 508, the patient monitor matches the features of the set of data with an appropriate output, or action using a lookup table. The lookup table may be similar to the one described above, with reference to FIG. 4. Although not shown, the patient monitor can encode the features into different categories prior to using the lookup table. Upon completing the lookup and performing the associated action, the process 500 repeats itself as needed throughout the operation of the device.

FIG. 6 is a flow chart illustrating an embodiment of a process 600 implemented by a patient monitor for determining an appropriate action based on the features of physiological data, which can also be referred to as a set of data.

At block 604, the patient monitor obtains a set of data as described in greater detail above, with reference to block 502 of FIG. 5. At block 606, the patient monitor determines a first feature of the set of data. As described earlier, the feature can be any one of various general characteristics of the data including, slope, standard deviation, linear regression, correlation coefficient, differences between engine outputs, time domain, frequency domain, and the like. It is to be understood that features of data that can be abstracted are many, and should not be limited by the features specifically recited herein.

At block 608, the patient monitor determines a category within the first feature of the set of data. As described earlier, with reference to FIGS. 1, 2, and 3, the categories may take many different forms. For instance, as described above with reference to FIG. 1, if the abstracted feature is the slope of the set of data, the categories may be represented as a number of different slopes, and encoded using bit codes. Thus, the patient monitor will determine the proper slope, or category, that should be associated with the set of data.

In the example illustrated in FIG. 2, the abstracted feature is the difference between engine outputs, and the categories can be insignificant difference, minor difference, and significant difference. Thus, the patient monitor determines which category is appropriate for the difference between data 206 and 208 in time segment 210A of FIG. 2.

Similarly, the patient monitor can determine the appropriate category for the standard deviation, linear regression, correlation coefficient, and/or trend line of data measurements, as described above with reference to FIG. 3. In an embodiment, the number of different categories within a feature is finite and/or predetermined. In another embodiment, the categories are determined dynamically during process 600. In an embodiment, the categories are implemented using bit codes. In another embodiment, the categories are implemented using an alphanumeric code, or word. Furthermore, the categories of each feature may be different. For instance, one feature may have two categories and another feature may have ten or more features. Furthermore, the different categories of a feature can based on the type of data, the type of physiological data, the type of feature, the type of analysis being performed, or the like.

At block 610, the patient monitor encodes the selected category to be used when looking up the appropriate action in a lookup table. The patient monitor can encode the category in any number of different ways and use any number of different bits and/or bytes to do so. In an embodiment, the categories are represented as different sequences of bits and/or bytes, or bit codes. The patient monitor uses the bit codes to look up the appropriate output in the lookup table. Other methods of encoding the data are envisioned without departing from the spirit and scope of the description. For example, the different categories may be represented using some alphanumeric code or word, or the like.

At determination block 612, the patient monitor determines if there are additional features of the set of data to be analyzed. As described above in greater detail with reference to FIG. 4, more than one feature can be used in the lookup table to select the appropriate action. Thus, at block 612, the patient monitor determines if an additional feature of the set of data is to be analyzed. If there is an additional feature of the set of data to be analyzed, the patient monitor determines the additional feature of the set of data, as illustrated at block 614. Block 614 is similar to block 606, described above. At block 616, the patient monitor determines a category within the additional feature of the set of data, similar to block 608, described above. At block 618, the patient monitor encodes the category to use with the lookup table, as described above with reference to block 610.

After encoding the category, as illustrated at block 618, the patient monitor again determines if there is an additional feature to be analyzed, as illustrated at block 612. If there are additional features, the patient monitor continues to analyze the additional feature(s), determine the category within the additional feature(s) and encode the category, as illustrated in blocks 614, 616, and 618, respectively. Once there are no additional features, the patient monitor looks up the action corresponding to the one or more encoded categories, as illustrated at block 620.

To determine the appropriate action based on the encoded categories, the patient monitor can use a lookup table, similar to the LUT 400 described above, with reference to FIG. 4. Using the lookup table, the patient monitor can account for all of the different categories of the different features that were previously analyzed and determine the appropriate action. In an embodiment, abstracting features and using the lookup table reduces the number of computations processed by the patient monitor.

At block 622, the patient monitor performs the appropriate action based on the output of the lookup table. In an embodiment, the patient monitor repeats process 600 as desired.

It is to be understood that the different actions that can be performed by the patient monitor are many. For example, the patient monitor may determine that the appropriate action includes changing a display or output, activating an alarm, gathering additional data via the sensor, the internet or some other means, notifying a healthcare provider, the patient or another person, powering off, requesting additional information from a user, etc. Thus, the various actions that may be performed should be construed broadly.

Although described in terms of a patient monitor and physiological data, the processes described above, may be carried out using any number of general computing devices such as a personal computer, tablet, smart phone, and the like. As described above, abstracting features, or general characteristics, of data and then performing some type of action based on the general characteristics, or features, of the data rather than the data itself can significantly decrease processing resources. The process can be useful whenever abstracting and processing features would use fewer processing resources than processing the data itself or where a number of different potentials options are available and undefined states would be harmful.

For example, in an embodiment, the table of FIG. 4 can be used in conjunction with a system that automatically changes display characteristics based user proximity. In an embodiment in a system that tracks proximate users, the abstraction system described and table of FIG. 4 can be used to determine screen changes based on proximate user preferences. There can be a number of potential inputs used in determining screen orientation. These can include proximity to the screen in distance, hierarchy of proximate users, alarms relevant to proximate users, etc. Each of these inputs act as the signal abstractions and each will receive an appropriate bit code that can be used with the table of FIG. 4 to determine a solution. In an embodiment, use of the signal abstractions reduces the number nested if/then statements in software and simplifies the ability to encode for every possible solution.

FIG. 7 illustrates an embodiment of a patient monitoring system 700 capable of abstracting features of physiological data, as described above with reference to FIGS. 1-6. The patient monitoring system 700 includes a patient monitor 702 attached to a sensor 706 by a cable 704. The sensor monitors various physiological data of a patient and sends signals indicative of the one or more parameters to the patient monitor 702 for processing.

The patient monitor 702 generally includes a display 708, control buttons 710, and a speaker 712 for audible alerts. The display 708 is capable of displaying readings of various monitored patient parameters, which may include numerical readouts, graphical readouts, and the like. Display 708 may be a liquid crystal display (LCD), a cathode ray tube (CRT), a plasma screen, a Light Emitting Diode (LED) screen, Organic Light Emitting Diode (OLED) screen, or any other suitable display. The patient monitor 702 may monitor SpO₂, Hb, HbO₂, SpHb™, SpCO®, SpOC™, SpMet®, PI, PVI®, PR, temperature, and/or other parameters.

An embodiment of a patient monitoring system 700 according to the present disclosure is capable of measuring and displaying trending data of the various parameters and preferably is capable of conducting data analysis as to the trending. Furthermore, the patient monitoring system is capable of abstracting features of the physiological data being monitored. In an embodiment, the patient monitor 702 includes an abstraction module for carrying out the processes described above. It is to be understood by one skilled in the art that the patient monitor 702 may come in various, shapes, sizes and configurations without departing from the spirit and scope of the description. For example, the patient monitor 702 may be larger, smaller, portable, comprise varying size displays 708, and the like.

The sensor 706 may be one of many different types. For example, the sensor 706 may be disposable, reusable, multi-site, partially reusable, partially disposable, be adhesive or non-adhesive, monitor the physiological parameters using reflectance, transmittance, or transreflectance, and may be placed on a finger, hand, foot, forehead, neck, or ear, and may be a stereo sensor or a two-headed sensor. Thus, one of skill in the art will appreciate that sensor 706 may be any number of different types of sensors without departing from the spirit and scope of the disclosure.

FIG. 8 illustrates an example noninvasive multiparameter physiological monitor 800 that can implement any of the features, processes, steps, etc., described herein. An embodiment of the monitor 800 includes a display 801 showing data for multiple physiological parameters. For example, the display 801 can include a CRT or an LCD display including circuitry similar to that available on physiological monitors commercially available from Masimo Corporation of Irvine, Calif. sold under the name Radical™, and disclosed in U.S. Pat. Nos. 7,221,971; 7,215,986; 7,215,984 and 6,850,787, for example, the disclosures of which are hereby incorporated by reference in their entirety. In an embodiment, the multiparameter patient monitor includes an abstraction module for performing the processes described above. Many other display components can be used that are capable of displaying respiratory rate and other physiological parameter data along with the ability to display graphical data such as plethysmographs, respiratory waveforms, trend graphs or traces, and the like.

The depicted embodiment of the display 801 includes a measured value of respiratory rate 812 (in breaths per minute (bpm)) and a respiratory rate waveform graph 806. In addition, other measured blood constituents shown include SpO₂ 802, a pulse rate 804 in beats per minute (BPM), and a perfusion index 808. Many other blood constituents or other physiological parameters can be measured and displayed by the multiparameter physiological monitor 800, such as blood pressure, ECG readings, EtCO₂ values, bioimpedance values, and the like. In some embodiments, multiple respiratory rates, corresponding to the multiple input sensors and/or monitors, can be displayed.

FIG. 9 illustrates an embodiment of a sensor system 900 including a sensor assembly 901 and a monitor cable 911 suitable for use with any of the physiological monitors shown in FIGS. 7 and 8. The sensor assembly 901 includes a sensor 915, a cable assembly 917, and a connector 905. The sensor 915, in one embodiment, includes a sensor subassembly 902 and an attachment subassembly 904. The cable assembly 917 of one embodiment includes a sensor 907 and a patient anchor 903. A sensor connector subassembly 905 is connected to the sensor cable 907.

The sensor connector subassembly 905 can be removably attached to an instrument cable 911 via an instrument cable connector 909. The instrument cable 911 can be attached to a cable hub 920, which includes a port 921 for receiving a connector 912 of the instrument cable 911 and a second port 923 for receiving another cable. In certain embodiments, the second port 923 can receive a cable connected to a pulse oximetry or other sensor. In addition, the cable hub 920 could include additional ports in other embodiments for receiving additional cables. The hub includes a cable 922 which terminates in a connector 924 adapted to connect to a physiological monitor (not shown).

In an embodiment, the acoustic sensor assembly 901 includes a sensing element, such as, for example, a piezoelectric device or other acoustic sensing device. The sensing element can generate a voltage that is responsive to vibrations generated by the patient, and the sensor can include circuitry to transmit the voltage generated by the sensing element to a processor for processing. In an embodiment, the acoustic sensor assembly 901 includes circuitry for detecting and transmitting information related to biological sounds to a physiological monitor. These biological sounds can include heart, breathing, and/or digestive system sounds, in addition to many other physiological phenomena. The acoustic sensor 915 in certain embodiments is a biological sound sensor, such as the sensors described herein. In some embodiments, the biological sound sensor is one of the sensors such as those described in the '883 Application. In other embodiments, the acoustic sensor 915 is a biological sound sensor such as those described in U.S. Pat. No. 6,661,161, which is incorporated by reference herein in its entirety. Other embodiments include other suitable acoustic sensors.

The attachment sub-assembly 904 includes first and second elongate portions 906, 908. The first and second elongate portions 906, 908 can include patient adhesive (e.g., in some embodiments, tape, glue, a suction device, etc.). The adhesive on the elongate portions 906, 908 can be used to secure the sensor subassembly 902 to a patient's skin. One or more elongate members 910 included in the first and/or second elongate portions 906, 908 can beneficially bias the sensor subassembly 902 in tension against the patient's skin and reduce stress on the connection between the patient adhesive and the skin. A removable backing can be provided with the patient adhesive to protect the adhesive surface prior to affixing to a patient's skin.

The sensor cable 907 can be electrically coupled to the sensor subassembly 902 via a printed circuit board (“PCB”) (not shown) in the sensor subassembly 902. Through this contact, electrical signals are communicated from the multi-parameter sensor subassembly to the physiological monitor through the sensor cable 907 and the cable 911.

In various embodiments, not all of the components illustrated in FIG. 9 are included in the sensor system 900. For example, in various embodiments, one or more of the patient anchor 903 and the attachment subassembly 904 are not included. In one embodiment, for example, a bandage or tape is used instead of the attachment subassembly 904 to attach the sensor subassembly 902 to the measurement site. Moreover, such bandages or tapes can be a variety of different shapes including generally elongate, circular and oval, for example. In addition, the cable hub 920 need not be included in certain embodiments. For example, multiple cables from different sensors could connect to a monitor directly without using the cable hub 920.

Additional information relating to acoustic sensors compatible with embodiments described herein, including other embodiments of interfaces with the physiological monitor, are included in U.S. patent application Ser. No. 12/044,883, filed Mar. 7, 2008, entitled “Systems and Methods for Determining a Physiological Condition Using an Acoustic Monitor,” and U.S. Pat. Application No. 61/366,866, filed Jul. 22, 2010, entitled “Pulse Oximetry System for Determining Confidence in Respiratory Rate Measurements,” the disclosures of which are hereby incorporated by reference in their entirety. An example of an acoustic sensor that can be used with the embodiments described herein is disclosed in U.S. Pat. Application No. 61/252,076, filed Oct. 15, 2009, titled “Acoustic Sensor Assembly,” the disclosure of which is hereby incorporated by reference in its entirety.

Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment.

Depending on the embodiment, certain acts, events, or functions of any of the methods described herein can be performed in a different sequence, can be added, merged, or left out all together (e.g., not all described acts or events are necessary for the practice of the method). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores, rather than sequentially.

The methods, steps, processes, calculations, computations or the like (“methods”) provided herein are simplified examples that are generally performed by advanced processing devices, including complex signal processors, sensitive analog and digital signal preprocessing boards, optical/optoelectronic componentry, display drivers and devices, or similar electronic devices. An artisan will recognize from the disclosure herein that the various methods often must be performed at speeds that, as a practical matter, could never be performed entirely in a human mind. Rather, for many calculations providing real time or near real time solutions, outputs, measurements, criteria, estimates, display indicia, or the like, many of the foregoing processing devices perform tens to billions or more calculations per second. In addition, such processing devices may process electrical signals, infrared signals, wireless signals, or other electro-magnetic wave signals that are incomprehensible to a human mind in their raw form and at the speeds communicated.

The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both operating in real-time or near real-time and at speeds unattainable by a human. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The blocks of the methods and algorithms described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.

While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments of the inventions described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain inventions disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. 

1-20. (canceled) 21-23. (canceled)
 24. A patient monitoring system comprising: one or more processors communicatively coupled with a physiological sensor that is configured to emit light towards a tissue site, detect the light after it has interacted with tissue, and output a first sensor signal responsive to the detected light, the one or more processors configured to: receive the first sensor signal from the physiological sensor, wherein the first sensor signal corresponds to a plethysmographic signal; identify a first feature associated with the first sensor signal, wherein the first feature is a frequency domain feature; compare the first feature to a plurality of categories, wherein each category of the plurality of categories corresponds to a different category value; select a category of the plurality of categories that most closely matches the first feature; combine a first category value corresponding to the selected category with a second category value corresponding to a second feature associated with a second sensor signal; and output an indication of a physiological parameter based at least in part on the first category value and the second category value.
 25. The patient monitoring system of claim 24, wherein the one or more processors are further configured to receive the second sensor signal from the physiological sensor.
 26. The patient monitoring system of claim 24, wherein the one or more processors are further configured to receive the second sensor signal from a sensor other than the physiological sensor.
 27. The patient monitoring system of claim 24, wherein the physiological parameter comprises at least one of respiratory rate, pulse rate, perfusion index, or blood pressure.
 28. The patient monitoring system of claim 24, wherein the one or more processors are further configured to determine a plethysmograph waveform from the first sensor signal, wherein the first feature corresponds to the plethysmograph waveform.
 29. The patient monitoring system of claim 24, wherein the first feature corresponds to at least one of a trend line, a standard deviation, a slope, a change in the slope, a correlation coefficient, or a linear regression.
 30. The patient monitoring system of claim 24, wherein at least one of the first category value or the second category value comprises at least one of a bit code, a sequence of bits, a sequence of bytes, or an alphanumeric code.
 31. A patient monitoring system comprising: one or more processors communicatively coupled with a physiological sensor that is configured to emit light towards a tissue site, detect the light after it has interacted with tissue, and output a first sensor signal responsive to the detected light, the one or more processors configured to: receive the first sensor signal from the physiological sensor; identify a first feature associated with the first sensor signal; select, from a plurality of categories, a category that most closely matches the first feature, wherein to select the category the one or more processors configured to compare the first feature to the plurality of categories; identify a first category value corresponding to the selected category; and output an indication of a physiological parameter based at least in part on a combination of the first category value and a second category value corresponding to a second feature associated with a second sensor signal.
 32. The patient monitoring system of claim 31, wherein the one or more processors are further configured to receive the second sensor signal from the physiological sensor.
 33. The patient monitoring system of claim 31, wherein the one or more processors are further configured to receive the second sensor signal from a sensor other than the physiological sensor.
 34. The patient monitoring system of claim 31, wherein the physiological parameter comprises at least one of respiratory rate, pulse rate, perfusion index, or blood pressure.
 35. The patient monitoring system of claim 31, wherein the first feature corresponds to at least one of a trend line, a standard deviation, a slope, a change in the slope, a correlation coefficient, or a linear regression.
 36. The patient monitoring system of claim 31, wherein each of the plurality of categories correspond to a different candidate feature associated with the first feature.
 37. The patient monitoring system of claim 36, wherein the first feature corresponds to a slope, and wherein each of the plurality of categories correspond to a different candidate slope.
 38. The patient monitoring system of claim 31, wherein at least one of the first category value or the second category value comprises at least one of a bit code, a sequence of bits, a sequence of bytes, or an alphanumeric code.
 39. The patient monitoring system of claim 31, wherein the first feature comprises at least one of a time domain feature or a frequency domain feature.
 40. A method for reducing processing load of a patient monitor in communication with a physiological sensor, the physiological sensor configured to emit light towards a tissue site, detect the light after it has been attenuated by tissue, and output a first sensor signal responsive to the detected light, the method comprising: receiving the first sensor signal from the physiological sensor; identifying a first feature associated with the first sensor signal; selecting, from a plurality of categories, a category that most closely matches the first feature, wherein said selecting the category comprises comparing the first feature to at least two of the plurality of categories; identifying a first category value corresponding to the selected category; and outputting an indication of a physiological parameter based at least in part on a combination of the first category value and a second category value corresponding to a second feature associated with a second sensor signal.
 41. The method of claim 40, wherein the second sensor signal is received from the physiological sensor.
 42. The method of claim 40, wherein the second sensor signal is received from a sensor other than the physiological sensor.
 43. The method of claim 40, wherein at least one of the first category value or the second category value comprises at least one of a bit code, a sequence of bits, a sequence of bytes, or an alphanumeric code. 